Improve CVE alias status normalization#2058
Open
shensz2017 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Skill Improvement ($50-150 Bounty)
Skill Modified
Skill name:
cve-triageSkill path:
skills/vuln-management/cve-triage/SKILL.mdWhat Was Wrong
The CVE triage flow parsed CVE IDs and then moved directly into CVSS, KEV, EPSS, SSVC, and SLA assignment. It did not explicitly normalize advisory aliases or check source lifecycle status before scoring. That can create duplicate remediation tickets for the same vulnerability (
CVE-*,GHSA-*, OSV, vendor advisory, distro advisory) or over-prioritizeREJECTED,RESERVED, withdrawn, duplicate, orDISPUTEDrecords.Related review issue: #2057
What This PR Fixes
REJECTED,RESERVED, withdrawn, or duplicate CVEs from receiving active CVSS/EPSS/SSVC priority as if they were live vulnerabilities.DISPUTEDrecords and low-confidence alias mappings.Evidence
Before (skill could over-prioritize this):
After (now correctly handled):
Test Cases Added/Updated
tests/vulnerable/cve-triage-rejected-alias-duplicated-as-active.yamltests/benign/cve-triage-canonical-alias-status-reviewed.yamlgit diff --check,git diff --cached --check, and key-field checks for the new YAML evidence files.Bounty Tier
Bounty Info